actually, I take this back.
Having releaseIfNotNull(x) when x cannot be null is confusing.
Here is one case : depending on how I read the code, I get contradictory information : from the constructor, mTable cannot be null, but here it may be...
I'd prefer if we use x.close()/x.release() directly if x cannot be null.