Based on the CFGLoopEntrance element, it is possible to have a CFG driven LocationContext update which contains loop information as well.
Updated the loop unrolling feature as well to use purely the LocationContext stack and not implement its own.
In the current situation the loop unrolling keeps track the currently simulated loop by having a stack of loops. However, the elements of the stack (so the needed information to describe the currently simulated loop) contains not just a Stmt* but a LocationContext* too which is a stack as well. So in order to store this information more efficient and intuitive I have added it to the LocationContext stack.