The queryutil code doesn't know about $atomic, so an operation with the query

{ a:1, $atomic:true }

will be treated in queryutil like

{ a:1, b:1 }

. Because of the extra field, the query optimizer won't create an optimal plan on index

{ a:1 }

and will instead try both

{ a:1 }

and

{ $natural:1 }

.