Fix: LoopSolver has to execute the criteria regardless of the verbosity mode

In the current implementation this caused different solution behavior depending
on the chosen verbosity mode. Plain stop critera
were ignored in the SOLVER::QUIET case.

This patch fixed the problem.