This is not the same behavior as before, since the limits have not been checked by registerParameter. But since the limits are not checked later on (no Parameter->setValue(d) existing any more), it seems reasonable to introduce this check on initialization.

add explicit parameter methods to avoid error prone string-defined access; enhance unit tests accordingly

Remove some trivial or obscure tests.

Redmine: #1965