LocalClassHydrator assumes incorrect order for fields

[Machine-Maker]

In determining captured values in the LocalClassHydrator, it assumes an incorrect order of fields, breaking out a loop to collect fields before all captured values have been collected.

class Demo {

	Demo(String arg1, String arg2) {
		
		class Other {
			private final String innerValue = "test";

			public String toString() {
				return arg2 + this.innerValue;
			}
		}

		new Other().toString();
	}
}

The above example produces a list of fields that begins with the "innerValue" field, then the 1 val$arg2 field, then the this$0 field.