So far I have been building my project with the CRT dll statically linked to the executable. However I have no particular reason to do this other than this idea of mine that if I don't do it, users without the msvcrt.dll won't be able to run the application.
Question though is, is this expected when the target systems are windows 2000 and up?
Another question is, when I run the dependency walker on my executable, it still lists msvcrt.dll as a dependency and the dll shows as loaded on Process Explorer. What gives? Why is the dll loaded when I have it linked statically?