Add a debug mode to check that Reducer remove functions are inverse of add

[jberdine]

It would be possible to add a less efficient debug mode where each time each Reducer's remove function is called, its value is compared to the result of computing the accumulated value using add.

It is a user programming error for remove to return a non-null value that is different from that computed using add, and it would be helpful to detect such errors.