[Alfa1]

I have been running vb3 on my big board since 2005 and have not suppressed error reporting. So stating that errors were hidden since 2002 is complete nonsense.

You can spin it however you like, but warnings are intended so that the developers pick up on it and do something about it. It is not good practice at all to hide warnings.

Deprecated errors are a big sign on the wall that the software you run is getting outdated and should be either fixed or replaced by modern software. Because sooner or later your server software like php version will be EOL and you risk all. PHP 5.3 is already EOL. PHP 5.4 will be.
Just like YUI2 has been EOL since 2009 and YUI is abandoned now. But we see no rewrite going on replacing YUI with jquery. Its just waiting for the hammer to fall.
Hiding the warnings is like fixing the security vulnerability by completely removing the install folder. It sort of works, but it evidently shows that quick hacks are provided instead of quality development.

In the case of vb4 you can wait until it stops working, hope that Internet Brands actually fixes up vb4, releases a quality vb6 or draw your conclusions based upon the current situation.