Factorize 12010258260, if you're slow, you're the human.

I know a Secretary of State who told the UN Security Council that Iraq had weapons of mass destruction.

He lied.

It would give the theory that sword-wielding skeletons were involved in the Peloponnesian War a fair chance.

No, it is not just "a" ReadByte snippet. It is a ReadByte snippet which (modulo: variable-names; bracketing of if-clauses; expansion of macros; and whitespace) is equal to the ImageMaster code, with one possible exception (MaxExtents doesn't look like a macro, if it is an element of an enum, it isn't an exception).
Code which does the same, will look the same. But there will often be differences at details, even differences which compilers don't wipe away. And that is why I am surprised by the disassembled code, "index + 2 > 2048" is equal to "index > 2046" (and "index + 6 > 2048" is equal to "index > 2042") if one ignores overflow. Bug-to-bug compatibility is relevant, but I am at a loss why creating map/mp would be important (unreachable memory is only useful if other buggy code looks at that memory, and it is initialized if 2042 <= index < 2046)
This is bla-bla; I wrote it, but didn't check it.