One I personally logged had to do with methods documented as “Always throws”.

There exists several methods in the framework like Convert.ToDecimal(DateTime) that do nothing but throw an exception. The response was that the methods exist to allow easier conversion from VB6.

What scares me is that that suggests that the methods exists so that VB6 code copied to VB.NET will compile without error rather than attempting to follow a well-known axiom of getting the compiler to detect logic errors whenever possible. Rather than providing a compile error and forcing someone to fix the problem before releasing the software, these methods allow the software to compile and it’s then the onus of the unit tests or the testers to find the runtime error.