Ordered query tables don't have wrong counter updated properly

Today at a client, we had an ordered query table which had two correct lines, and should have 17 wrongs, i.e. missing entries. The test surprisingly turned green with 0 errors, 0 failures, and 0 exceptions. It was not reproducible with no results delivered from the query() function, so this issue probably just occurs when there are some rights in the ordered query table. Query and subset query table were not affected by this (we changed the table type while exploring around this issue).