> I've never seen this as a problem - it's rare to be messing with TRIS
> bits on anything other than I2C pins, so normally you know the fixed
> bits of the TRIS value to write during the I2C code, and if you do
> need to TRIS-twiddle outside the I2C code,  the code that does this
> will know what state to leave the I2C pins (i.e. idle)  in as I2C bus
> will probably be inactive outside of the I2C code.

Also, one can let FSR point to TRISA/B and then bit-access both PORT
and TRIS bits without switching banks all the time!