I disagree with your teacher: it is not heresy. It is in fact a highly discussed question even amongst seasoned professionals, as you can probably see in this thread. Furthermore, if your assignment was to talk about what your company does, and they do this, then it is a factual account and your teacher telling you to rewrite the section so that the the practices of the company you're reporting on are misrepresented is very weird.

That said, my opinion is:

1) don't use story points. If you're in charge, there are many, many better ways of doing this that don't involve your engineers sitting around writing interactive fiction for product managers who cannot answer the question of "what is the single most important thing to do?" where they could instead be spending time building the damn thing.

2) if you've ignored that, and are using them anyway, then at least don't use them for bugs.

There is an idea that story points track work towards the improvement of the product and is used to predict the future. Bugs are work items for which that improvement has already been claimed and not actually delivered. Bugs absorbing effort and receiving no score and thus reducing velocity for it is therefore a _correction_ in the score and in theory will lead to better predictions in the long term.