Remove ongoing oracle reports

[cag]

Affects #37

[cag]

@xavierlepretre For context, that change was implemented in #53. Those changes also included a change to the interface.

Yeah, it's a little less efficient than straight assembly because the arr[i] notation does bounds checking. There are some scenarios when the optimizer might be able to catch that this is unnecessary, but in general, without something like native iterator support or way to hint to the compiler that bounds checks should be skipped in the language, this would be hard to optimize away on the bytecode level.

Anyway, this is way more readable.