What would the point be though, if you are sure you want to throw the error anyway? Or if you combo it with a normal "enforce", to avoid the lazy penalty?

As far as I can tell (but I could be wrong), the only point of onOutOfMemory is for using it as a callback?