That'd require keeping track of which behavior classes have been verified, and disassociate the error from the code that provoked it. Could remove the call in the constructor and put an explicit call to verifySettings after creating an instance - but since there isn't a way to modify settings after a behavior has been bound, that doesn't seem necessary.