If you're ever in doubt on using the checked keyword in C# or the /checked compiler directive because it might hurt your performance then don't worry anymore.
I did some integer additions on my portable in a checked and unchecked context and the performance decrease was only about 3-5% on operations of about 5 seconds. Don't forget that checked and unchecked only have an effect on integers. Float and double never check for overflows and the decimal always does. More info on this feature can be found on msdn and in this Code Project article
This is the code I used to benchmark the performance of a checked vs unchecked context. I also tested subtraction, multiplication and division with similar results. Pay great attention when using the checked context. Only inline operations are checked/unchecked, code in function calls and anonymous functions isn't.
using System; using System.Diagnostics; namespace GISSolved.TestConsole { class Program { static void Main(string[] args) { GC.Collect(3, GCCollectionMode.Forced); var checkedResult = TimeIt(true); Console.WriteLine("Checked : {0}", checkedResult); GC.Collect(3, GCCollectionMode.Forced); var uncheckedResult = TimeIt(false); Console.WriteLine("Unchecked : {0}", uncheckedResult); Console.WriteLine("Difference : {0:0}%", (1 - ((double)checkedResult / (double)uncheckedResult)) * 100); Console.ReadLine(); } static long TimeIt(bool isCheckedCalculation) { var s = new Stopwatch(); s.Start(); Int32 a = 123, b = 123; if (isCheckedCalculation) { checked { for (int i = 0; i < 900000000; i++) { a = i + b + a; a = 125; } // extra check to make sure that overflow exceptions are thrown try { Int32 x = a + Int32.MaxValue; } catch (OverflowException) { Console.WriteLine("Int32 Overflow"); } } } else { unchecked { for (int i = 0; i < 900000000; i++) { a = i + b + a; a = 125; } Int32 x = a + Int32.MaxValue; } } s.Stop(); return s.ElapsedMilliseconds; } } }