The point is, all values of the int are available. Null is stored somewhere outside the underlying int.

It was just a question about the syntax used - why type Nullable<int> when there is direct syntactical support in C# for nullable types - in this case you could simply type int? rather than Nullable<int>

At the very least Nullable<T> is a lot friendlier to search than T? if you want to learn more on the subject.

not everyone is familiar with C#, and Nullable<int> conveys better meaning in writing to that kind of audience.

int? is syntactic sugar for Nullable<int>, which didn't seem worth getting into :-)