> we have plenty of places to fix in opm-core and the other modules if you want to be that nit-picky...

Sure.  But this particular instance was a case of `int ->  size_t` to *work around a warning*.  I'm just saying we should use the correct solution when we go through the trouble of implementing a solution at all.