I would really like if you could add SVG (Scalable Vector Graphics) to the available diagram export formats.

SVG is the most suitable format for many applications. Certainly it is the best for showing diagrams on the web (although browsers still need plugins for viewing, but Mozilla is on the way with native support). XSL-FO processors like FOP also prefer SVG.

Native CVS support in EA would be a good argument for me to have when trying to convince the people in the software standards group of my organization. CVS is now our (mandatory) company standard version control system.

Open source SCC-to-CVS proxies (Igloo) are not 100% reliable (and not completely open source because the SCC is a Microsoft secret). Besides, SCC is not 1-to-1 compatible with CVS, so it would be nice if EA knew the CVS interface natively.

The best solution would be if locking and version control were integrated.Ideally, the whole project would be kept in the version control system, and when someone wants to edit something, he checks it out (and hereby lock it). When he finishes editing, he checks it in (and hereby unlocks it). That is how we work on source code. The model should be no different.

As far as I was aware, it is impossible to have packages (and classes etc.) on diagrams if they are not also in the tree, so I am unable to help you (except to suggest that you look extra carefully to find it!).