Case 1: \fbox cannot enclose characters tightly
Why don't \fbox and PSTricks \psframebox enclose its contents accurately? In my opinion, every edge should exactly touch the outer part of its contents. Does changing font solve this issue?
\documentclass{article}
\usepackage[english]{babel}
\usepackage{pstricks}
\fboxsep=0pt
\fboxrule=0.001pt
\begin{document}
\color{red}\fbox{\color{black}3}
\end{document}

This funny feature might be the source of problem where pdfcrop accidently trims grid labels.
Case 2: \fbox cannot enclose PSTricks grid labels
It is another example where \fbox and \psframebox cannot accurately enclose their contents.
\documentclass{article}
\usepackage[english]{babel}
\usepackage{pstricks}
\fboxsep=0pt
\fboxrule=0.001pt
\begin{document}
\color{red}
\fbox{\color{black}%
\pspicture[showgrid](3,3)
\endpspicture
}
\vspace{1cm}
\psframebox[framesep=0pt,linewidth=0.001pt,linecolor=red]{%
\pspicture[showgrid](3,3)
\endpspicture
}
\end{document}
Should the frames enclose the grid labels? In my mental model, they should.

Questions
In my mental model, \fbox should enclose its contents tightly when \fboxsep=0pt without allowing any part of its contents to reside outside its frame.
If \fbox allows any part of its contents to live outside its frame, what is \fbox actually for?
Why wasn't \fbox defined to enclose its contents based on the most left, right, bottom, top parts? I think it is more useful, right?

\fboxis a frame around boxes, not a frame around characters – Herbert Jun 13 '11 at 20:28\fboxdefined to enclose its contents based on the most left, right, bottom, top parts? – xport Jun 13 '11 at 21:39\fboxis considered to be more of a decorative box than you hope. After all, it has the tuning parameter\fboxsepindicating how far from the "real" box the frame should be drawn, and by default, it is not zero. – Ryan Reich Jun 13 '11 at 21:56