Math in loops gets compiled

Floati's just-in-time compiler now compiles the common Math functions -> Math.floor, round, abs, sqrt, min, max, pow, sin, cos and the rest -> when they are called inside a hot loop. Graphics, physics, audio and data code lean on these constantly, and until now every call dropped back to the slower interpreter path. Now the whole loop, including the Math calls, runs on the fast path, even when the calls are nested (like Math.max(Math.floor(x), y)) or mixed with array work. In our benchmarks a loop chaining floor, abs and sqrt over a million values runs about twice as fast. It calls the exact same built-in function the interpreter would, so results are identical to the last decimal. And it stays honest: if a page has replaced one of the Math functions with its own, or is using a different Math object, Floati notices at the start of the loop and simply runs it the normal way. With this, loops made of plain numbers, array elements, bitwise work and Math calls -> the great majority of number-heavy code -> now tier up to compiled speed. The full engine test suite passes identically with the speed-up switched on and off.