>The concern is that a BINDEVENT() is like setting a time bomb at execution time. Unless the programmer is well aware that BINDEVENT()s are active s/he will likely observe 'unexplainable' processing paths being executed.

I saw the same disadvantage with ACCESS and ASSIGN methods.

> I can see benefit to adopting some standardized place to put these lines simply for future reading of the code for debugging/enhancement purposes.

I can't see any reason to arbitrarily restrict the design.

I can see issues with documentation, commenting, and developer training.
Particularly a skilled contractor being followed by a maintenance programmer who doesn't even know what BINDEVENTS() does - or that it even exists.