Interestingly, they don't mention their latest incarnation of "DLL hell," the multiple versions of the same libraries which are used by different pieces of their own system.
If they use a DLL version x for a component A and a version y for a component B, they raised memory usage only for convenience of not updating one of the components to use the latest version of the DLL.
http://blogs.technet.com/b/askcore/archive/2008/09/17/what-i...
If they use a DLL version x for a component A and a version y for a component B, they raised memory usage only for convenience of not updating one of the components to use the latest version of the DLL.