Add debug code to add a clock to the Run-Mat optionally called by the password lock function.
The code is now commented out. It works, more or less, but at random times there will be system errors about an illegal address access.
This will have to wait until we can run code from a memory location out of the stack and permanently save it there (so that it still runs after the add-in exits).
This experiment let me understand that (at least a part of) the add-in's code is kept in memory after APP_RUNMAT is called from it.