Fix BRM's SetMin/Maximum to actually work.

BRMs should not assume that the value is under the new maximum.
The consequence was that in setRange, the new maximum would be
the current value. Same was true for setMinimum.