Many DBMSes including Oracle do not have a Boolean column type, so this may explain why there is no Boolean field type in ArcGIS either.
@Emily's suggestion of using a coded value attribute domain is a good one and I believe this is the ESRI-recommended best practice.
The only other suggestion I would have is to use a CHAR field of length 1, as this way you can use the slightly more descriptive "Y" or "N", or "T" or "F", rather than 1's or 0's, and, according to this article, in Oracle 1-character CHAR columns are actually more efficient than 1-digit NUMBER columns.
1or0, any other is not possible. A short int with length of 1 allows any of 0 thru 9. When a feature class is edited by many people it's hard to ensure they all know what to use. – matt wilkie♦ Apr 23 '12 at 20:02