Explicit nulling, though that is seldom necessary. Perhaps one can view it as a form of defensive programming.
Use it (or nullable(T) structure for non-nullables) as a flag to indicate a missing field when mapping fields from one data source (byte stream, database table) to an object. It can get very unwieldy to make a boolean flag for every possible nullable field, and it may be impossible to use sentinel values like -1 or 0 when all values in the range that field is valid. This is especially handy when there are many many fields.
Whether these are cases of use or abuse is subjective, but I use them sometimes.