Thanks for confirming.
To me, this seems to be a bug, but I can't say whether it's in the map routines or in the Big Integers library. I have, for now, resorted to putting the string representation of the big integer into the map (just as you suggested), but that's also a performance penalty since I am invoking "ToString" quite a number of times.
Regards,