#Reedbeta - yup it is strong statement. I personally also use it for some projects, and it is really good to work inside. As I mentioned, I was speaking about compiler quality (not the IDE) -> If I get some time today I'll post some assembly output from VS/Gcc/Clang for you to compare.
This probably won't give you problems as long as you stay in VS and Windows, but basically developing things like operating systems is just close-to-impossible in VS (due to compiler).
Also I mentioned standards. VS native C compiler hasn't got any single existing standard (not ansi, not c89, not c99, not c11, not gnu-extended c, etc.) it seems like using some Microsoft's own standard (and it is really messy) -> developing any C application in VS is a pain. This is quite a problem, because all libraries should have C interface (for portability & usage in other languages -> that is with C++ close to impossible).
As for standard libraries shipped with VS, they have severe bugs. STL doesn't support aligned memebers in containers (however according to stdlibc++ and stl specifications it SHOULD), some STL functors have different behaviour than the standard says, somehow MS prefers it's own system functions over LIBC ones (which makes annoying thousands of warning lines during compilation), etc. Though these things can be ignored or better "repaired" (by using some different implementations of standard libraries) -> but why can't Microsoft at least use standards and clean standard libraries?