Improving the explanation of 'Captured by Closures'

The new alternative suggestion actually results in the expected behaviour, rather than simply avoiding the runtime exception
Improving the code snippet and candidate answers for 'Captured by Closures'

- Moving 'values' out of scope of the function invocation
- Adding 'value not found' detail to 'does not compile' sample answer
- (nonexistent) ArrayIndexOutOfBoundsException -> IndexOutOfBoundsException
- changed the last sample answer to "both print 120, 120, 120"