No excpetions allowed? Than using "new" is the wrong choice! Redefining the "new" operator only makes sense when you can reuse existing code, but if you must ad

No excpetions allowed? Than using "new" is the wrong choice! Redefining the "new" operator only makes sense when you can reuse existing code, but if you must add that check for everey "new" invocation, then you are forced to parse all your existing code and using a separate function makes sense. Sorry for your colleagues, but this is not a problem with undefined behaviour: it's the original developer fault! And I'd hate if compilers were forced to restrain themselves from helping smart developers in order to please loosy developers.