CtoB: not page-boundary safe

[damianut]

CtoB function is not page-boundary safe.

As mud-freak wrote here:

In the second line within the function, reading an integer (four bytes) instead of one byte might read across page boundaries in memory. How ever small the chances are of that ever happening - it did!. See more details in the linked post. This issue was then addressed in MEM_ReadByte (Ikarus). MEM_ReadByte is, of course, the better choice here than reading an integer when only interested in the first byte. For further discussion, it might be best to move to the Ikarus-thread in the editing section of the forum, to not go too far off-topic here.