Part of the problem has been explained after I looked at the client's site. My colleagues thought they were running one procedure while they were running FIFO version of the procedure which is much more complex. So, the 1.91 (in fact, 1.91718) value is indeed the procedure result although it's not clear why would it have calculated that value.