Getting ready for Nullable Reference Types
There are some disadvantanges about this solution. You not only loose the argument-name inside the exception but if you are using ReSharper then you won't be able to quick-fix this in future.

Thus I think it's not necessary to create such helpers because as soon as the new feature is there, ReSharper will probably have nice quick-fix for that so it'll turn all if(foo == null) throw new ArgumentException(..) into the new syntax. I doubt ReSharper will be able to quick-fix this.

Besides if you properly decorate your code with the [NotNull] and [CanBeNull] attributes, you are half-way safe. Since I started using them, It's been ages that I last saw a NullReferenceExcepiton or ArgumentNullExcepiton.



I also find ReSharper's naming convention more appealing. This means 


Some becomes NotNull and
Option becomes CanBeNull