What does LoadLibrary do if you give it the name of a DLL already statically linked to?

On Windows, what will LoadLibrary do if you give it the name of a DLL that your executable already statically linked (aka implicitly linked) to? Will two copies of the DLL be loaded? What if the pathname of the DLL is some sort of alias for the original? For example, say I run the executable as X:\myprog\myexe.exe, and it implicitly links to X:\myprog\mydll.dll, but I pass LoadLibrary \\the\unc\path\to\X\myprog\mydll.dll. Is LoadLibrary smart enough to resolve these to the same DLL?