The calculus method is vastly less computational effort than the method you describe.
You calculate $\frac{\mathrm{d}}{\mathrm{d}x} \left( r(x) - c(x) \right)$ once. This difference is a quadratic polynomial, so the computation is multiplying one constant by $2$ and writing down the resulting answer -- nearly effortless. Then evaluating this to find the cost of one additional unit of production requires one multiplication by a constant and one addition by a constant. This can, with a little practice, be done (or at least estimated) in your head.
Your method requires cubing both $10$ and $11$, squaring both $10$ and $11$, eight constant multiplication and eight additions/subtractions. This is not the sort of computation (or even estimate) nearly anyone can do in one's head. (When I competed in mental mathematics, this would have been at the edge of my abilities and would have required several restarts and re-computes to verify I hadn't mangled any of the many intermediate results.)
Equally useful... Time doing it both ways for $+1$, $+2$, and $+4$, that is, compare production of $10$ items with the options to produce $11$, $12$, and $14$ items. Now compare the time spent to the magnitude of the errors. Certainly, the "multiply the first derivative by the number of additional items" approximation method gets worse for large production changes and is low quality when the second derivative is large. (How bad ... is covered in Taylor series, with the keyword "error term", typically covered in "Calculus 2". Without diving into too many details, you can use the second derivative evaluated at the starting point and the change in production to bound how large an error you can make using this approximation method. For very many students, this is the first approximation method which comes with a computable (in-)accuracy bound, vastly improving on just waving hands and saying "approximately". In fact, if the bound is too large (so a large error is possible) you also gain the tools to compare the computational cost of using more derivatives in the approximation versus picking a starting point closer to the target production versus restarting the computation from scratch.)
Finally, the problem is unrealistic in that one seldom has an analytic expression for costs and revenue. One may have a point estimate for costs and revenue at the current production level and estimates of "elasticity" in these numbers. Again avoiding too many details, this corresponds to knowing the first derivatives of cost and revenue. So, in addition to letting you use an easy estimation technique and presenting an approximation technique for which you can compute bounds on the badness of the approximation, you also start practicing using the sort of data you will actually be able to obtain in real life.