I've run into an interesting, and I would way somewhat annoying, behavior related to this discussion....

Let's say that you have registered more than one class with the same name... here's a simple example -- you have a class called MyClass in "C:\My Documents." Then, you move MyClass somewhere else and register it again....

... well, regardless of which class you add to the project references, when using CreateObject(), VB grabs the first instance it finds in the registry when creating the object. I have run into this several times, and you might, too.... The NEW keyword always grabs the Project Reference file, while CreateObject might not.

I don't think this is necessarily a reason not to use CreateObject() -- it's just a gotcha to be aware of....