The algorithm isn't part of the results. The results are what you learned from the project - the knowledge. In this case it would be the analysis of the performance on the specified problem. The algorithm is what you built to get the results, not the results themselves.
But with the current outline, it looks like you will have to put too much into the introduction. You need to describe, somewhere, the problem and current solutions and why you want a new algorithm. That seems like a lot for the intro. Likewise you need a conclusion putting the results in context.
Note that while most of your work may have been in developing the algorithm, that isn't the essence of your knowledge contribution. The essence is in why and how this was a good approach to a problem (properly quantified) in the first place.
For example, if I build a better garbage collector for, say, Ruby, the knowledge contribution is in how and why this approach is better than other GC systems, if, indeed, it is. But you can even get a thesis out of the work if you show that the approach, which seemed promising, in fact is worse, on some scale. It is the knowledge we require, not the software/algorithm.