The description of CoLoadLibrary() says it does pretty much the same as LoadLibraryEx() – loads a DLL into the process. COM classes creation functions – CoCreateInstance() and CoGetClassObject() – both do load the necessary DLL into the process too.
Then why is CoLoadLibrary() needed in the first place and how should it be used?
Have a look at the code:
So it just calls:
Presumably, the routine merely exists for backwards compatibility — it probably has its roots in Win16.