Throw out-of-range exceptions when a state variable is assigned a value outside its declared range

[gfrances]

Currently, for range variables, whenever the application of an action results in some (range) state variable taking a value outside its declared range, the action is implicitly considered as non-applicable.
This is useful, but too often leads to subtle model bugs that are hard to debug. A better approach would be to leave to the modeler the responsibility of keeping those variables well within its range. Whenever an action which is considered applicable (its preconditions being satisfiable) results in an out-of-range value, a runtime out-of-range exception should be thrown.