That's an interesting answer. I guess I'm just confused. If you divide something by 100, you end up with two decimal places, period. ...
But, grasshopper, you are forgetting that the computer does not operate in the decimal realm. It operates in the binary realm. What you think is 342/100, the computer sees as:
101010110/1100100
What you see as 2-1.94, the computer computes as, generally speaking,
10-1.1111 = .0000111
If you convert 1.1111 (binary) back to decimal, you will get 1.9375.
A silly extension of this (1.94 conversion) to many decimal/binimal places:
1.1111000010100011110101110000101000111101011100001 (binary) =
1.9399999999999995026200849679298698902130126953125 (decimal), and
1.11110000101000111101011100001010001111010111000011 (binary) =
1.94000000000000039079850466805510222911834716796875
You can see that one bit at 49 binimal places still has a not insignificant effect on the value of the number.
And for .06:
0.100110011001100110011 (binary) =
.599999904632568359375 (decimal), and
0.1001100110011001100111 (binary) =
.6000001430511474609375 (decimal)
Only rarely can real decimal numbers be exactly represented by real binary numbers. 'Real numbers' here means floating point numbers, as opposed to whole (integer) numbers. Why? In decimal, the number to the right of the '.' are 1/10, 1/100, 1/1000, etc. In binary, those numbers are 1/2, 1/4, 1/8, 1/16, etc. They only rarely align.
People have tried to get rich adding up these lost millicents and microcents. Well, at least they've tried in the movies.