Studio vs DVX: The winner is ...

After trying out both Studio and DVX, I have now decided about which tool to choose: It will be Studio.

And I will now also sign a maintenance contract for Studio; it will probably not be able to run without constant support. I will also take a webinar for Studio upgraders on 8 January, and take the certification exam.
The main reasons for my choice:
Studio +:
+ Handling of "rouge codes" does not cause any extra work
+ AutoSuggest, that is so superior to DVX AutoAssemble
+ SDL Automatic Translation Server, which actually boost productivity
+ Dual editor has a better user interface
+ TW_users list is a good free source for support
Studio -:
- Multiple translations problem
- Instability and error messages
- Bad concordance search compared with Workbench
- Numbers and codes "localization" cannot be turned off
DVX +:
+ Intuitive and fast on the fly editing in all databases
+ The AutoAssemble and Lexicon function is very good in some cases
DVX -:
- Multiple translations problem
- Tags handling can become overwhelming in some Word documents
- Déjà vu users lists is only for DVX fanatics
It is difficult to compare the two systems function by function, as they are working so differently. Actually, you could have use of both AutoSuggest/AutoAssemble in the same system, and that also goes for the AutoSuggest dictionary/Lexicon as they could complement each other.