Why are we not to throw these exceptions?

Question

I came across this MSDN page that states:

Do not throw Exception, SystemException, NullReferenceException, or IndexOutOfRangeException intentionally f

Answer 1

Putting the discussion about NullReferenceException and IndexOutOfBoundsException aside:

What about catching and throwing System.Exception. I've thrown this type of exception in my code a lot and I was never screwed by it. Similarly, very often I catch the unspecific Exception type, and it also worked pretty well for me. So, why is that?

Usually users argue, that they should be able to distinguish error causes. From my experience, there are just a very few situations where you would want to handle different exception types differently. For those cases, where you expect users to handle errors programmatically, you should throw a more specific exception type. For other cases, I'm not convinced by the general best practice guideline.

So, regarding throwing Exception I don't see a reason to prohibit this in all cases.

EDIT: also from the MSDN page:

Exceptions should not be used to change the flow of a program as part of ordinary execution. Exceptions should only be used to report and handle error conditions.

Overdoing catch clauses with individual logic for different exception types are not best practice, either.