Profiling bytecode about battlecode2014

[chrisdembia]

I tried using Clock.getBytecodeNum(); at the beginning and end of a method to see how much bytecode one function used. Then I looked at the output of javap ... for that same method, with the intent of being able to interpret javap .... It helped a little; I was off by 1 kinda (the in-code difference gave 41 sometimes, and 11 other times; the bytecode difference with javap was about 40).

I think what we can do for now, aside from looking at javap ... (which is really easy and nice! though hard to interpret), is, just before calling yield(), set an indicator string to the # of bytecode used in that turn.