The profiling report provides instruction counts for each function. This is useful, but it would also be useful to have a profiling report which states how many times each instruction in the compiled code is executed. This would help when it comes to identifying hot spots inside functions. Such a report should be easily generated from the execution history. This instruction-level profiling report can be integrated with the object code pretty-printing, extended with #51, for easier reading.