Is it still the case that the bytecode viewer in IDEA doesn’t properly reflect the final Java class output? Simple things like

(0..10).forEach { … }

cause an

IntRange

and an iterator to be allocated. If I recall correctly calls like that are supposed to be optimized.

It's unstable feature with many restrictions. I usually run

javap -v

for generated classes, and it works OK