Fix range estimation bug in FPOptimizer

This fixes the main issue raised by #366 (the wrong optimization of the ```1/abs(x)<2``` term). Patch is self explanatory.
This was an unrelated bug that caused a compile error when enabling verbose debugging output