This is probably not the exact answer you are looking for, but I hope it is usefull.
The best solution I've come across to the model-documents problem is to arrange your project tree (the packages in the project browser, that is) so that every package, diagram, element and so forth is arranged in the precise order it sould come out in the hard-copy doc.
I do not the Use Case View, Dynamic View, Logical... arrangement, but instead I create a package with the appropriate title, which is the title I want to see at the top the hard copy documentation. I also write a small description of the project or subsystem in the "Note:" section of the package. Under this project package, I usually begin with a "1. Requirements" package that contains a requirements diagram, with all formal requirements, and so forth; then I create a "2. Business process" package, under the project package, with the processes diagrams and their description; then "3. Use cases", with use cases, and interaction diagrams under their corresponding use case... and so forth.
This way, when I generate the RTF (right-click on the project package, Documentation, Rich Text...) the documentation comes out in the appropriate order for formal system documentation.
You can play with the RTF generation options, for a finer result, and there are lots of tricks you can come out with to make the document much nicer. But the main issue here is that you should achieve locality of change/maintenance for your model and your hard-copy documentation.
The documents I have been able to produce this way have proved to be excellent as formal descriptions (those that have to be approved and signed by the customer) of the projected system or as guides to the system once it has been build. And the economy of time we have been able to achieve is surprising.
